Welcome Guest, you are in: Login
CTS Futures

Page History: Logout

Compare Page Revisions



« Older Revision - Back to Page History - Newer Revision »


Page Revision: 2012/09/04 17:16


Session Termination

Upon an established TCP (socket) connection, the T4 FIX API basic requirement is to have both the Initiator and Acceptor start with sequence number 1. The client will initiate the FIX Session by sending a Logon Message to the T4 FIX API server. Sucessful authentication will be responded with a Logon message echo. The Password field (Tag 96) of the API server logon message will be identified with an asterisk.

Drop of a physical connection will result in the end of a FIX Session. Upon reconnection, the client will attempt to start a new FIX Session with sequence number 1. Likewise, the T4 API server will respond with messages starting with sequence number 1.

Authentication Requirements

Following a sucessful physical connection to the T4 FIX API server, authenticated access is achieved with the following parameters of the Logon message:

Tag NameTag NumberDescription
1.TargetCompId56FIX API System
2.SenderCompId49Firm Name
3.SecureData91Application ID
4.SecureDataLen90Length of Application ID string
5.SenderSubId50Firm User Name (Trader name, desk, etc.)
6.RawData96Firm User Password
7.RawDataLen95Length of Firm Password string

Failure to provide the correct parameters in the Logon message will result in an logon failure. Appropriately, a Logout message will be sent to the client. The Logout message will contain a short description of the failure to help the firm determine the cause of failed authentication. Thereafter, a physical disconnection will occur. As the FIX Session failed, the T4 FIX API will expect a new attempt for a new FIX session. Therefore, the next Logon message (from the client) must start with sequence number 1.

Message Dictionary

TagField NameReq'dComments
Standard HeaderYMsgType = A
58Text|| N|| Free format text string. Contains informations related to the cause of the logout.
354|| EncodedTextLen|| NMust be set if EncodedText field is specified and must immediately precede it.
355EncodedText|| N Encoded (non-ASCII characters) representation of the Text field in the encoded format specified via the MessageEncoding field.
Standard TrailerY

Sample Message


Client Request

34=2|49=test|56=T4Test|52=20120904-22:13:57.789|
[FIXLOGOUT]
[MsgSeqNum] 34 = 2
[SenderCompID] 49 = test
[TargetCompID] 56 = T4Test
[SendingTime] 52 = 20120904-22:13:57.789

Server Response

34=2|49=T4Test|56=test|50=T4FIX|52=20120904-22:13:57.789|58=Successful logout upon request|
[FIXLOGOUT]
[MsgSeqNum] 34 = 2
[SenderCompID] 49 = T4Test
[TargetCompID] 56 = test
[SenderSubID] 50 = T4FIX
[SendingTime] 52 = 20120904-22:13:57.789
[Text] 58 = Successful logout upon request

Trade how you want, where you want

support@ctsfutures.com (312) 939 0164

2 Pierce Pl, Suite 200, Itasca, IL 60143

© 2009-2023 Cunningham Trading Systems LLC All rights reserved.